home *** CD-ROM | disk | FTP | other *** search
- Date: Tue, 31 May 1994 19:47:42 -0400 (EDT)
- From: Timothy Miller <millert@undergrad.csee.usf.edu>
- Subject: Re: MAUS
- To: gem-list@world.std.com
- In-Reply-To: <memo.253871@cix.compulink.co.uk>
- Message-Id: <Pine.3.87.9405311942.C27706-0100000@undergrad>
- Mime-Version: 1.0
- Precedence: bulk
-
-
-
- On Tue, 31 May 1994, Andre Willey wrote:
-
- >
- > In-Reply-To: <Pine.3.87.9405311330.A24733-0100000@undergrad>
- >
- > In <Pine.3.87.9405311330.A24733-0100000@undergrad>,
- > millert@undergrad.csee.usf.edu wrote:
- >
- > > No, the problem is not 'selecting all'. If it were shift-F5 or
- > > something nearly impossible to hit accidentally, then I'd never have
- > > brought it up. The problem is the fact that it's too easy yo hit
- > > and causes a tremendous amount of damage.
- >
- > NO. 'Select all' never causes any damage at all, in any application
- > that I'm aware of. It's what you do *next* that matters. If Atari Works
- > deletes the whole of a document as a result of typing a single character
- > when the entire document is already selected, then it should be summarily
- > taken out and shot.
- >
- > Andre
- >
-
- Right, but what happens next ALWAYS happens. Select-All is not the source
- of the problem (from some point of view or other), but what happens next
- would never destroy the document if the document had not been selected.
- If Ctrl-A did not select the whole document, then the following keypresses
- would not destroy the document. Therefore, get rid of Ctrl-A and you have
- solved the problem.
-
-